home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Nebula 2
/
Nebula Two.iso
/
SourceCode
/
MiscKit1.7.1
/
MiscKitArchive.mbox
/
mbox
/
000171_misckit-reques…aska.et.byu.edu_Thu Apr 7 03:40:43 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-30
|
3KB
Return-Path: <misckit-request@alaska.et.byu.edu>
Received: from alaska.et.byu.edu by darth.byu.edu (NX5.67d/NX3.0M)
id AA12342; Thu, 7 Apr 94 03:40:36 -0600
Received: from nexus.yorku.ca by alaska.et.byu.edu; Thu, 7 Apr 1994 02:10:22 -0600
Received: from monkey.circus.yorku.ca ([130.63.216.22]) by nexus.yorku.ca with SMTP id <9218>; Thu, 7 Apr 1994 04:10:22 -0400
Received: by monkey.circus.yorku.ca (NX5.67e/NX3.0M_DA_Jan30-93)
id AA03389; Thu, 7 Apr 94 04:07:20 -0400
From: "David Aspinall" <dave@circus.yorku.ca>
Message-Id: <9404070807.AA03389@monkey.circus.yorku.ca>
Subject: Re: MiscKit.pkg
To: misckit@alaska.et.byu.edu
Date: Thu, 7 Apr 1994 04:07:18 -0400
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1822
<< section where we thank all the contributors for their work .. deleted >>
<< some really excellent work though ... :) >>
My $.02:
I like the the idea of a pkg, although to be honest I am one of those
people who would insist on compiling it myself. I always hold onto the
previous source when I compile a new release just in case there is some
BIG problem with the new release.
What I would like is to .. maybe .. split the kit up into logical units.
Rather than one big 50 Mb kit, and one 6Mb debug library, why not
several. Now I know setting this up could take alot of work so I'm not
really pushing, just suggesting.
What I'm thinking of is kinda a hierarchy of dependance. Sort of like
how you (probably) couldn't use IndexingKit without using the Appkit
(although I haven't tried this). So we might start with
MiscFoundation
MiscString and other base level data structures
MiscFind
Its already a partioned project, why not a separate library.
Dependant on a compiled MiscFoundation library.
MiscAppkitExtensions
Views, buttons, sliders, anything that is directly connected to the
appkit, or maybe MiscInterfaces. I know the palettes are already
separate libraries, but they could be consolidated.
Dependant on a compiled MiscFoundation library.
Anyway, the only reason I see this as having any merit (as an idea) is to
collect sections that are not changing as often, and hold them at one
release. This way you only have to compile the kit that changes and the
dependent kits. Even then you don't have to distribute dependent kits if
they haven't changed, the end users simply have to rebuild the
dependancies.
Personally I prefer one big kit, a cohesive well thought out whole, but
for those who might be juggling disk space this might help.
David
(it sounds like a good idea at 4am...)